Wireless communication system and method

ABSTRACT

A method for processing wireless data in a wireless communication network, the wireless communication network including a plurality of intermediary nodes and a plurality of destination devices. The method includes determining at least one transmission path to each of the plurality of intermediary nodes. The at least one transmission path includes data associated with every intermediary node along the at least one transmission path. The method also includes determining a transmission path identifier for each of the at least one transmission paths and sending transmission data to at least one destination device of the plurality of destination devices. The transmission data is sent based on at least one of the transmission path identifiers.

PRIORITY

This application is a division of application Ser. No. 11/882,223, filedJul. 31, 2007 now U.S. Pat. No. 7,995,524, which claims the benefit ofU.S. Provisional Application No. 60/842, 675, filed Sep. 7, 2006, theentire contents of all of which are incorporated herein by reference.

TECHNICAL FIELD

The present disclosure relates generally to methods and devices forwireless communication systems and, more particularly, to wirelesscommunication systems, methods, and devices including control nodes,intermediary nodes, and destination nodes.

BACKGROUND

Due to an increasing number of wireless devices and a growing demand forwireless services, wireless communication systems continue to expand. Tomeet the growing demand, wireless providers have deployed a greaternumber of wireless transmitters. As an alternative, however, wirelessproviders have also utilized relay-based systems.

In a relay-based system, one node of a wireless system may communicatewith another node in the wireless system using one or more intermediarynodes, called relay nodes. In some systems, the relay node may bereferred to as a relay station, and the combination of nodes andconnections between an originating node and a destination node may bereferred to as a transmission path. Relay-based systems may be found inany type of wireless network.

An example of a relay-based system is a multi-hop relay (MR) network.FIG. 1 is a diagram of an exemplary prior art MR network 100 based onthe Institute of Electrical and Electronics Engineers (IEEE) 802.16family of standards.

As shown in FIG. 1, MR network 100 may include one or more transmitters,e.g., base station (BS) 110, one or more relay stations (RS) 120,including RSs 120 a, 120 b, and 120 c, and one or more subscriberstations (SS) 130, including SSs 130 w, 130 x, 130 y, and 130 z.

In MR network 100, communication between a transmitter station (e.g., BS110) and subscriber stations (e.g., SS 130 w, SS 130 x, SS 130 y, SS 130z, etc.) may be achieved using one or more relay stations (e.g., RS 120a, RS 120 b, RS 120 c, etc.). For example, in MR network 100, RS 120 amay receive data from BS 110 and send the data to another relay station(e.g., RS 120 b). Alternatively, RS 120 a may receive data from asubordinate relay station (e.g., RS 120 b), and send it to BS 110. Asanother example, RS 120 c may receive data from RS 120 b and send thedata to a supported subscriber station (e.g., SS 130 w). Alternatively,RS 120 c may receive data from a subscriber station (e.g., SS 130 w),and send it to a dominant relay station (e.g., RS 120 b).

Some embodiments, such as MR network 100, may use a scheduling algorithmby which subscriber stations (e.g., SS 130 w, SS 130 x, SS 130 y, SS 130z, etc.) may compete only once for initial entry into the network (i.e.,the communication network provided by serving BS 110 to subscriberstations within range). Once initial entry into the network isaccomplished, access slots may be allocated by BS 110. In otherembodiments, access slots may be dynamically allocated in each frameinterval. In either case, the access slots may be enlarged orcontracted, but the access slot remains assigned to a specificsubscriber station, thereby precluding the use of the access slot byother subscriber stations.

FIG. 2 illustrates an exemplary Media Access Control (MAC) frame formatbased on the IEEE 802.16 family of standards using OrthogonalFrequency-Division Multiple Access (OFDMA). As shown in FIG. 2,transmission time may be divided into variable length sub-frames: anuplink (UL) sub-frame and a downlink (DL) sub-frame. Although not shownin detail, the UL sub-frame may include ranging channels, a channelquality information channel (CQJCH), and UL data bursts containing data.

The DL sub-frame may include a preamble, a Frame Control Header (FCH), aDL-MAP, a UL-MAP, and a DL data burst area. The preamble may be used toprovide a reference for synchronization. For example, the preamble maybe used to adjust a timing offset, a frequency offset, and power. TheFCH may contain frame control information for each connection including,for example, decode information for SSs 130.

DL-MAP and UL-MAP messages may be used to allocate channel access fordownlink and uplink communication, respectively. That is, the DL-MAPmessage may provide a directory of access slot locations within thecurrent downlink sub-frame, and the UL-MAP message may provide adirectory of access slot locations within the current uplink sub-frame.In the DL-MAP message, this directory may take the form of one or moreDL-MAP Information Elements (MAP IEs). Each MAP IE in the DL-MAP messagemay contain parameters for a single connection (i.e., the connectionwith a single SS 130). These parameters may be used to identify where,in the current sub-frame, a data burst may be located, the length of thedata burst, the identity of the intended recipient of the data burst,and one or more transmission parameters.

For example, each MAP IE may contain a Connection ID (CID), identifyingthe destination device (e.g., SS 130 w, SS 130 x, SS 130 y, SS 130 z,etc.) for which a data burst is intended, a Downlink Interval Usage Code(DIUC), representing a downlink interval usage code by which downlinktransmission is defined, an OFDMA Symbol Offset, indicating the offsetof the OFDMA symbol in which a data burst starts, a sub-channel offset,indicating the lowest-index OFDMA sub-channel for carrying the burst,etc. Other parameters may also be included in the MAP IE including, forexample, a boosting parameter, a parameter indicating a number of OFDMAsymbols, a parameter indicating a number of sub-channels, etc. As usedherein, prior art MAC headers and MAP IEs may be referred to asconnection-switched control data.

DL-MAP and UL-MAP messages may each be followed by a data burst area.The data burst area may include one or more data bursts. Each data burstin the data burst area may be modulated and coded according to thecontrol type of a corresponding connection-switched control data. Forexample, referring to FIG. 3, MAP IE “w” may provide control informationfor data burst “w,” MAP IE “x” may provide control information for databurst “x,” MAP IE “y” may provide control information for data burst“y,” and MAP IE “z” may provide control information for data burst “z.”

Referring again to FIG. 1, BS 110 may receive data bursts for SS 130 w,SS 130 x, SS 130 y, and SS 130 z, each of which are subscriber devicesto RS 120 c. BS 110 may generate connection-switched control data foreach SS 130, inserting the connection-switched control data into a DLMAP IE slot of a frame. BS 110 may insert the associated data burst foreach SS 130 into a data burst area corresponding to eachconnection-switched control data. BS 110 may transmit the frame to thefirst node along the transmission path, i.e., RS 120 a. RS 120 a mayreceive the data, and process each connection-switched control data todetermine if any data is intended for a subscriber device of RS 120 a.If none of the data is intended for a subscriber device of RS 120 a, RS120 a may forward the data to the next RS 120 along the transmissionpath. In this example, none of the data is intended for a subscriberdevice of RS 120 a, and RS 120 a may transmit the data to RS 120 b.

Similarly, RS 120 b may receive the data, and process each control datato determine if any data is intended for a subscriber device of RS 120b. If none of the data is intended for a subscriber device of RS 120 b,RS 120 b may also forward the data to the next RS 120 along thetransmission path, i.e., RS 120 c. RS 120 c may receive the data, andprocess each control data to determine if any data is intended for asubscriber device of RS 120 c. In this example, SS 130 w, SS 130 x, SS130 y, and SS 130 z are subscriber devices of RS 120 c, and RS 120 c mayprocess the connection-switched control data, forwarding the appropriatedata to each SS 130 according to the transmission parameters stored inthe MAP IE.

In MR network 100, each RS 120 along the transmission path may processevery connection-switched control data (e.g., MAC header and MAP IEs) inthe frame until the individual control data, and their associated data,reach their destinations. Thus, for example, each of theconnection-switched control data of FIG. 1 may be processed three timesbefore they reach their destination. This may cause significant usage ofsystem resources and corresponding transmission latency.

SUMMARY OF INVENTION

In one aspect, the present disclosure is directed to a method forprocessing wireless data in a wireless communication network, thewireless communication network including a plurality of intermediarynodes and a plurality of destination devices. The method includesdetermining at least one transmission path to each of the plurality ofintermediary nodes. The at least one transmission path includes dataassociated with every intermediary node along the at least onetransmission path. The method also includes determining a transmissionpath identifier for each of the at least one transmission paths, wherethe transmission path identifier is a destination node identifier, andsending transmission data to at least one destination device of theplurality of destination devices. The transmission data is sent based onat least one of the transmission path identifiers.

In another aspect, the present disclosure is directed to a wirelesscommunication station for wireless communication in a wirelesscommunication network, the wireless communication network including aplurality of intermediary nodes and a plurality of destination devices.The wireless communication station includes at least one memory to storedata and instructions and at least one processor configured to accessthe memory. The at least one processor is configured to, when executingthe instructions, determine at least one transmission path to each ofthe plurality of intermediary nodes. The at least one transmission pathincludes data associated with every intermediary node along the at leastone transmission path. The at least one processor is also configured to,when executing the instructions, determine a transmission pathidentifier for each of the at least one transmission paths, where thetransmission path identifier is a destination node identifier, and sendtransmission data to at least one destination device of the plurality ofdestination devices. The transmission data is sent based on at least oneof the transmission path identifiers.

In another aspect, the present disclosure is directed to a method forperforming data processing in an intermediary node. The method includesreceiving, by a reception unit, transmission data. The transmission dataincludes at least one first control data and at least one second controldata. Each of the at least one first control data includes a connectionidentifier, each of the at least one second control data includes atransmission path identifier, and the transmission path identifier is adestination node identifier. The method further includes processing, bythe reception unit, the transmission data and buffering, by a bufferunit in communication with the reception unit, the processed data. Inaddition, the method includes receiving, by a transmission unit incommunication with the buffer unit, the buffered data from the databuffer unit and performing pre-transmission processing on the buffereddata. The method additionally includes configuring, by a control unit incommunication with the reception unit, the buffer unit, and thetransmission unit, one or more reception parameters associated with thereception unit.

In another aspect, the present disclosure is directed to an intermediarynode for performing data processing in a wireless communication network.The intermediary node includes a reception unit operable to receive andprocess transmission data. The transmission data includes at least onefirst control data and at least one second control data. Each of the atleast one first control data includes a connection identifier, each ofthe at least one second control data includes a transmission pathidentifier, and the transmission path identifier is a destination nodeidentifier. The intermediary node further includes a buffer unit incommunication with the reception unit and configured to buffer theprocessed data and a transmission unit in communication with the bufferunit and configured to receive the buffered data from the data bufferunit. In addition, the intermediary node includes a control unit incommunication with the reception unit, the buffer unit, and thetransmission unit, and operable to configure one or more receptionparameters associated with the reception unit.

In another aspect, the present disclosure is directed to a method forprocessing data in a wireless communication network, the wirelesscommunication network including a plurality of intermediary nodes and aplurality of destination devices. The method includes receiving data fortransmission to at least one destination device of the plurality ofdestination devices and determining a transmission path to a destinationintermediary node. The at least one destination device communicates withthe destination intermediary node. The method further includes assigninga first control data to the data, the first control data including oneor more parameters associated with the at least one destination device.The method also includes assigning a second control data to the data,the second control data including a transmission path identifier, wherethe transmission path identifier is a destination node identifier. Inaddition, the method includes transmitting at least one transmissionframe along the transmission path, the at least one transmission frameincluding the data.

In another aspect, the present disclosure is directed to a wirelesscommunication station for wireless communication in a wirelesscommunication network, the wireless communication network including aplurality of intermediary nodes and a plurality of destination devices.The wireless communication station includes at least one memory to storedata and instructions and at least one processor configured to accessthe memory. The at least one processor is configured to, when executingthe instructions, receive data for transmission to at least onedestination device of the plurality of destination devices and determinea transmission path to a destination intermediary node. The at least onedestination device communications with the destination intermediarynode. The at least one processor is further configured to assign a firstcontrol data to the data, the first control data including one or moreparameters associated with the at least one destination device. The atleast one processor is also configured to assign a second control datato the data, the second control data including a transmission pathidentifier, where the transmission path identifier is a destination nodeidentifier. In addition, the at least one processor is configured totransmit the at least one transmission frame along the transmissionpath, the at least one transmission frame including the data.

In another aspect, the present disclosure is directed to a method forprocessing data by an intermediary node in a wireless communicationnetwork, the wireless communication network including a plurality ofintermediary nodes and a plurality of destination devices. The methodincludes receiving data, the data including destination device data forat least one destination device of the plurality of destination devices,at least one first control data, and at least one second control data.Each of the at least one first control data includes a connectionidentifier, each of the at least one second control data includes atransmission path identifier, and the transmission path identifier is adestination node identifier. The method further includes evaluating thetransmission path identifier in each of the at least one second controldata and processing the data based on the transmission path identifier.

In another aspect, the present disclosure is directed to an intermediarynode in a wireless communication network, the wireless communicationnetwork including a plurality of intermediary nodes and a plurality ofdestination devices. The intermediary node includes at least one memoryto store data and instructions and at least one processor configured toaccess the memory. The at least one processor is configured to, whenexecuting the instructions, receive data, the data including destinationdevice data for at least one destination device of the plurality ofdestination devices, at least one first control data, and at least onesecond control data. Each of the at least one first control dataincludes a connection identifier; each of the at least one secondcontrol data includes a transmission path identifier, and thetransmission path identifier is a destination node identifier. The atleast one processor is further configured to evaluate the transmissionpath identifier in each of the at least one second control data andprocess the data based on the transmission path identifier.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of an exemplary prior art Multi-Hop Relay (MR)network;

FIG. 2 illustrates an exemplary prior art MAC Frame Control format;

FIG. 3 illustrates an exemplary prior art MAP IE;

FIG. 4 is a block diagram of exemplary message processing in atag-switched network, consistent with certain disclosed embodiments;

FIG. 5 a is a block diagram of an exemplary Base Station (BS),consistent with certain disclosed embodiments;

FIG. 5 b is a block diagram of an exemplary Relay Station (RS),consistent with certain disclosed embodiments;

FIG. 5 c is a block diagram of an exemplary Subscriber Station (SS),consistent with certain disclosed embodiments;

FIG. 6 a illustrates an exemplary tag-switched data processing,consistent with certain disclosed embodiments;

FIG. 6 b illustrates an exemplary tag-switched data processing,consistent with certain disclosed embodiments;

FIG. 6 c illustrates an exemplary tag-switched data processing,consistent with certain disclosed embodiments;

FIG. 7 a is a flow chart illustrating an exemplary BS Downlinkprocessing, consistent with certain disclosed embodiments;

FIG. 7 b is a flow chart illustrating an exemplary RS Downlinkprocessing, consistent with eel lain disclosed embodiments;

FIG. 8 a is a flow chart illustrating an exemplary BS Uplink processing,consistent with certain disclosed embodiments;

FIG. 8 b is a flow chart illustrating an exemplary RS Uplink processing,consistent with certain disclosed embodiments;

FIG. 9 is a block diagram illustrating an exemplary RS architecture,consistent with certain disclosed embodiments;

FIG. 10 is a flow chart illustrating an exemplary processing with RSarchitecture, consistent with certain disclosed embodiments; and

FIG. 11 is a system diagram illustrating exemplary data processing in anetwork, consistent with certain disclosed embodiments.

DETAILED DESCRIPTION

FIG. 4 is a block diagram of an exemplary tag-switched network 400,consistent with certain disclosed embodiments. A tag-switched network400 may be one in which one or more tags are used for routing dataand/or communications. In one exemplary embodiment, tag-switched network400 may be based on the IEEE 802.16 family of standards. As shown inFIG. 4, tag-switched network 400 may include one or more transmitters,e.g., base station (BS) 410, one or more relay stations (RS) 420,including RSs 420 a, 420 b, and 420 c, and one or more subscriberstations (SS) 430, including SSs 430 w, 430 x, and 430 y.

BS 410 may be any type of communication device configured to transmitand/or receive data and/or communications based on one or more wirelessstandards, many of which are known in the art. For example, BS 410 maybe configured to communicate with one or more SSs 430, RSs 420, one ormore other BSs 410, and/or other networks (not shown) using thecommunication protocols defined by the IEEE 802.16 family of standards.In some embodiments, BS 410 may also be referred to as, for example, aNode-B, a base transceiver system (BTS), an access point, etc.

As shown in FIG. 5 a, BS 410 may include one or more of the followingcomponents: at least one central processing unit (CPU) 411 configured toexecute computer program instructions to perform various processes andmethods, random access memory (RAM) 412 and read only memory (ROM) 413configured to access and store information and computer programinstructions, memory 414 to store data and information, one or moredatabases 415 to store tables, lists, or other data structures, one ormore I/O devices 416, one or more interfaces 417, one or more antennas418, etc. Each of these components is well-known in the art and will notbe discussed further.

Referring again to FIG. 4, in one exemplary embodiment, BS 410 may beconfigured to create and store one or more BS tag tables 440. BS tagtables 440 may include data associated with one or more nodes and/or oneor more transmission paths in tag-switched network 400. For example, BStag table 440 may include one or more relay node identifiers, one ormore transmission paths, and/or one or more transmission pathidentifiers, as well as relationships between the data. In addition, BStag table 440 may include other parameters, such as, for example,transmission parameters related to one or more transmission paths,transmission parameters related to one or more RSs 420, transmissionparameters related to one or more SSs 430, etc.

The one or more relay node identifiers may be used to uniquely identifyeach node in tag-switched network 400. The one or more nodes mayinclude, for example, BS 410, one or more RSs 420, and/or one or moreSSs 430. The one or more transmission paths may each include one or moreRSs 420 by which data may be routed through tag-switched network 400,and each transmission path may be uniquely identified by a transmissionpath identifier, which may be called a “tag” or “tag-switched connectionidentifier.” In one exemplary embodiment, the one or more transmissionpaths may also be known as the “relay paths.” In some embodiments, thedisclosed transmission method may be referred to as tunnel transmission,and the tag-switched connection identifier may be referred to as atunnel CID.

In one exemplary embodiment, the tag may serve as an index into BS tagtable 440. For example, the transmission path from BS 410 to RS 420 amay include RS 420 a, and may be identified by the tag “1.” Thetransmission path from BS 410 to RS 420 b may include RS 420 a and RS420 b, and may be identified by the tag “2.” Tag “3” may identify thetransmission path from BS 410 to RS 420 c which may include RS 420 a, RS420 b, and RS 420 c. In some embodiments, BS tag table 440 may beconfigured to uniquely identify more than one transmission path to oneor more RSs 420 in tag-switched network 400.

Alternatively and/or additionally, BS tag table 440 may identifyrelationships between one or more nodes in tag-switched network 400. Forexample, BS tag table 440 may identify subordinate and dominantrelationships between one or more nodes in tag-switched network 400. Inaddition, BS tag table 440 may identify a serving RS 420 or BS 410 foreach SS 430 in tag-switched network 400. The serving RS 420 or BS 410may be the node through which SS 430 transmits and/or receives data withtag-switched network 400. As shown in FIG. 4, RS 420 c is the serving RS420 for SS 430 w, SS 430 x, and SS 430 y. Thus, BS tag table 440 maycontain data associated with SS 430 w (i.e., CID=w), SS 430 x(i.e.,CID=x), and SS 430 y (i.e., CID=y).

BS 410 may also be configured to create one or more RS tag tables 450.RS tag tables 450 may include information associated with BS 410, one ormore RSs 420, and/or one or more SS 430. For example, RS tag tables 450may include one or more relay node identifiers, one or more transmissionpaths, and/or one or more transmission path identifiers. In addition, RStag tables 450 may include other parameters, such as, for example,transmission parameters related to one or more transmission paths,transmission parameters related to one or more RSs 420, transmissionparameters related to one or more SSs 430, etc.

In one exemplary embodiment, one or more RS tag tables 450 may beuniquely generated for each RS 420, and may include informationassociated with one or more transmission paths of which the particularRS 420 may be a node. Thus, for example, RS tag table 450 of one of RS420 may include data associated with all SSs 430 directly connected tothat RS 420 as well as all subordinate RSs 420. For example, referringto FIG. 4, RS tag table 450 a may include data associated with thetransmission path from BS 410 to RS 420 b, identified by tag “2,” andthe transmission path from BS 410 to RS 420 c, identified by tag “3,”both of which may include RS 420 a. Similarly, RS tag table 450 b mayinclude data associated with the transmission path from BS 410 to RS 420c, identified by tag “3,” which includes RS 420 b. In some embodiments,RS tag tables 450 may include data associated with one or more SSs 430.For example, RS tag table 450 c may include data associated with SS 430w (i.e., “w”), SS 430 x (i.e., “x”), and SS 430 y (i.e., “y”). In oneexemplary embodiment, tags stored in the tag-switched control data mayserve as indexes into the RS tag tables 450, and may allow each RS 420to perform routing and transmission of data according to the parametersfound in RS tag tables 450 and the tag-switched MAP Ms.

BS 410 may be configured to create and/or store one or more BS tagtables 440 and/or one or more RS tag tables 450 when there is any typeof change to tag-switched network 400. For example, BS 410 may createone or more BS tag tables 440 and/or RS tag tables 450 when tag-switchednetwork 400 is first established, when one or more RSs 420 are deployedin tag-switched network 400, when one or more RSs 420 are redeployed intag-switched network 400, and the like.

RS 420 may be any type of communication device configured to transmitand/or receive data and/or communications with one or more SSs 430, RSs420, and/or other BS 410 using the communication protocols defined byone or more wireless standards. In certain disclosed embodiments, RS 420may serve as an intermediary between one or more SSs 430, RSs 420,and/or BSs 410. For example, RS 420 may receive data from BS 410, andsend the data to one or more subordinating SSs 430 and/or RSs 420.Similarly, in the reverse direction, RS 420 may receive data from SS 430or a subordinate RS 420, and transmit the data to another RS 420 or BS410.

In addition, RS 420 may be configured to store and/or access one or moreRS tag tables 450. For example, as shown in FIG. 4, RS 420 a may storeRS tag table 450 a, RS 420 b may store RS tag table 450 b, and RS 420 cmay store RS tag table 450 c.

As shown in FIG. 5 b, RS 420 may include one or more of the followingcomponents: at least one central processing unit (CPU) 421 configured toexecute computer program instructions to perform various processes andmethods, random access memory (RAM) 422 and read only memory (ROM) 423configured to access and store information and computer programinstructions, memory 424 to store data and information, one or moredatabases 425 to store tables, lists, or other data structures, one ormore I/O devices 426, one or more interfaces 427, one or more antennas428, etc. Each of these components is well-known in the art and will notbe discussed further.

SS 430 may include any type of wireless client device configured tocommunicate with BS 410 and/or other SSs 430 and RSs 420 using one ormore wireless communication standards. SSs 430 may include, for example,servers, clients, mainframes, desktop computers, laptop computers,network computers, workstations, personal digital assistants (PDA),tablet PCs, scanners, telephony devices, pagers, cameras, musicaldevices, etc. In one exemplary embodiment, SS 430 may be a mobilecomputing device. In other embodiments, SS 430 may be a “non-mobile”computing device located in a mobile environment (e.g., airplanes,watercraft, buses, multi-passenger vehicles, automobiles, etc.).

As shown in FIG. 5 c, SS 430 may include one or more of the followingcomponents: at least one central processing unit (CPU) 431 configured toexecute computer program instructions to perform various processes andmethods, random access memory (RAM) 432 and read only memory (ROM) 433configured to access and store information and computer programinstructions, memory 434 to store data and information, one or moredatabases 435 to store tables, lists, or other data structures, one ormore I/O devices 436, one or more interfaces 437, one or more antennas438, etc. Each of these components is well-known in the art and will notbe discussed further.

In one exemplary embodiment, one or more DL-MAP and UL-MAP messages maybe used to allocate channel access for downlink and uplinkcommunication, respectively. That is, the DL-MAP messages may eachinclude one or more DL-MAP Information Elements (MAP IEs), and each ofthe one or more DL-MAP IEs may include parameters associated with anaccess slot within the current downlink sub-frame. The UL-MAP messagesmay each include one or more UL-MAP IEs, and each of the one or moreUL-MAP IEs may include parameters associated with an access slot withinthe current uplink sub-frame. Additionally and/or alternatively, one ormore Hybrid Automatic Repeat reQuest (HARQ) MAP messages may be used toallocate channel access for downlink and uplink communication. Forexample, the HARQ MAP messages may each include one or more DL- orUL-HARQ MAP IEs, and each of the one or more DL- or UL-HARQ MAP IEs mayinclude parameters associated with an access slot within the currentuplink or downlink sub-frame, i.e., HARQ data bursts. In one exemplaryembodiment, the DL- or UL-HARQ MAP IE may include a Reduced CID (RCID),identifying the destination device (e.g., SS 430 w, SS 430 x, SS 430 y,etc.) for which a data burst is intended. As used herein, MAP messagesmay include, for example, UL-MAP message, DL-MAP message, DL- and/orUL-HARQ MAP messages, etc.; MAP IEs may include, for example, UL-MAPIEs, DL-MAP IEs, DL- and/or UL-HARQ MAP IEs, etc.; and CIDs may include,for example, CIDs, RCIDs, etc.

FIG. 6 a illustrates an exemplary transmission of tag-switched controldata in connection with transmission of connection-switched control datafields in a tag-switched network, such as, for example, tag-switchednetwork 400, consistent with certain disclosed embodiments. As shown inFIG. 6 a, one or more connection-switched control data (i.e., MAP IEscontaining CIDs and/or RCIDs) may be replaced with a single tag-switchedcontrol data (i.e., MAP IE containing a tag), and the one or moreconnection-switched control data may be moved into data burst portion ofa sub-frame associated with the tag-switched control data. Thetag-switched control data may be used to transmit a frame along atransmission path from BS 410 to a destination RS 420. Theconnection-switched control data may be used by the destination RS 420to process and send the data to one or more SSs 430. The destination RS420 may be the serving RS 420 for the one or more SSs 430.

For example, tag-switched control data “3” may be stored in place of theCID (or RCID) in the MAP message area, and the connection switchedcontrol data, “w,” “x,” and “y” may be located in the data portion withtheir associated data bursts. Control data “3” may provide details as tothe location (e.g., position and length) of the control data and datafor “w,” “x,” and “y” in the data burst portion of the frame. Becausethe tag-switched control data identifies the transmission path, thetag-switched control data may use only those transmission parametersrelated to the relay links. For example, the tag-switched control datamay contain a tag value to identify a transmission path to serving RS420, DIUC for the relay link, parameters identifying the location of thedata in the current frame, etc.

Thus, the single tag may be used to identify and administer allconnections along a single transmission path. In one exemplaryembodiment, each RS 420 along the transmission path would maintain an RStag table 450 identifying the connections along the transmission path,and may be capable of forwarding the data to the next node until thedestination node is reached. In another exemplary embodiment, routinginformation may be embedded in the transmission path ID, and one or moreassociated instructions may be stored in memory during pre-configurationor signaling. In this manner, RS 420 may be configured to access theinstructions, decode the transmission path ID, and forward the datawithout accessing RS tag table 450. Once the packet data arrives at thedestination node, the destination node may be configured to unpack andprocess the frame data and send the data burst to the destinationdevice, i.e., SS 430.

For example, referring again to FIG. 4, BS 410 may transmit data bursts(i.e., data bursts w, x, and y) to one or more SSs 430 by means of asingle frame. Instead of using a plurality of control data, eachcontaining a CID or RCID, BS 410 may use a single tag-switched controldata containing a tag which identifies the transmission path. Forexample, BS 410 may transmit data to SS 430 w, SS 430 x, and SS 430 y,each of which are subordinate to RS 420 c, by identifying the commontransmission path to RS 420 c. Thus, BS 410 may use the singletag-switched control data for processing through intermediate RS 420 aand RS 420 b, replacing three connection-switched control data with thesingle tag-switched control data identifying the transmission path to RS420 c, which provides service to SS 430 w, SS 430 x, and SS 430 y.

FIG. 6 b illustrates exemplary transmission of tag-switched control dataprior to transmission of connection-switched control data fields in atag-switched network, such as, for example, tag-switched network 400,consistent with certain disclosed embodiments. As shown in FIG. 6 b,tag-switched control data (i.e., MAP IE containing a tag) in frames maybe used in conjunction with one or more connection-switched control data(i.e., MAP IEs containing CIDs and/or RCIDs) in other frames to transmitdata. For example, a tag-switched control data in a first frame mayprovide transmission path routing information for one or moreconnection-switched control data contained in the data burst portion ofsub-frames in one or more subsequent frames. The tag-switched controldata may be used to transmit a frame along a transmission path from BS410 to a destination RS 420. The connection-switched control data may beused by the destination RS 420 to process and send the data to one ormore SSs 430. The destination RS 420 may be the serving RS 420 for theone or more SSs 430. In one exemplary embodiment, the subsequent frameis immediately subsequent. Alternatively and/or additionally, thesubsequent frame may be any frame which follows a first frame containingthe tag-switched control data associated with the subsequent frame.

For example, tag-switched control data “3” may be stored in place of theCID (or RCID) in the MAP message area of a first frame, and theconnection switched control data, “w,” “x,” and “y” may be located inthe data portion of the same frame. The data associated with thetag-switched control data “3” may provide details as to where thecontrol data for “w,” “x,” and “y” may be found in the data burstportion of the same frame. In addition, tag-switched control data “3”may provide details as to where the data for “w,” “x,” “y” may be foundin the data burst portion of a subsequent frame. Because thetag-switched control data identifies the transmission path, thetag-switched control data may use only those transmission parametersrelated to the relay links. For example, the tag-switched control datamay contain a tag value to identify a transmission path to serving RS420, DIUC for the relay link, parameters identifying the location of thedata in the current frame, parameters identifying the location of thedata in subsequent frames, etc.

FIG. 6 c illustrates exemplary transmission of tag-switched control datasubsequent to configuration of connection-switched control data fieldsin a tag-switched network, such as, for example, tag-switched network400, consistent with certain disclosed embodiments. As shown in FIG. 6c, connection-switched control data may be configured during connectionsetup. Configuration may include, for example, transmission of one ormore connection-switched control data identifying one or more data burstfields in subsequent frames. Thus, when one or more frames are sentsubsequently to the connection setup, the tag-switched control data(i.e., MAP IE containing a tag) may be used in conjunction with one ormore connection-switched control data (i.e., MAP IEs containing CIDsand/or RCIDs) configured during connection setup to transmit data. Inone exemplary embodiment, the subsequent frame may be any frame whichfollows the connection setup process.

For example, tag-switched control data “3” may be stored in place of theCID (or RCID) in the MAP message area of a first frame, and dataportions, “w,” “x,” and “y” may be located in the data portion of thesame frame. The data associated with the tag-switched control data “3”may provide details as to where the data portions for “w,” “x,” and “y”may be found in the data burst portion of the same frame. Theconnection-switched control data configured during connection setup maybe used to route the data for “w,” “x,” and “y” and may be found in thedata burst portion of that frame.

FIG. 7 a is an exemplary flow chart 700 a illustrating processing of adownlink communication sent from BS 410. BS 410 may receive data from anexternal network (step 705), and determine the destination SS 430 forthe data. Based on the destination SS 430, BS 410 may determine atransmission path (step 710), including a tag identifier. BS 410 mayallocate the resources along the transmission path (step 715). Inaddition, BS 410 may add one or more connection-switched control dataand one or more tag-switched control data, assigning transmissionparameters for both (step 720). BS 410 may then transmit the frame (step725).

FIG. 7 b is an exemplary flow chart 700 b illustrating processing of adownlink communication received by RS 420 from BS 410. RS 420 mayreceive frame data from BS 410 (step 750), identifying one or moretag-switched control data in the frame (step 755). RS 420 may check thetag-switched control data to determine if the frame is tagged for itself(step 760). If RS 420 determines that the frame is tagged for itself(step 760, Yes), RS 420 may unpack the data and decode theconnection-switched control data contained in the data burst area of theframe (step 765). In addition, RS 420 may send data associated with oneor more connection-switched control data to the SSs 430 identified bytheir respective connection-switched control data (step 770).

If RS 420 determines that the frame is intended for another RS 420 (step760, No), RS 420 may forward the data to the next RS 420 along thetransmission path. In one exemplary embodiment, RS 420 may access RS tagtable 450 and, using the tag as an index into the table, decode thetag-switched control data to determine the transmission path associatedwith the tag (step 775). In another exemplary embodiment, routinginformation may be embedded in the transmission path ID, and one or moreassociated instructions may be stored in memory during pre-configurationor signaling. In this manner, RS 420 may be configured to access theinstructions, decode the transmission path ID, and forward the datawithout accessing RS tag table 450.

Based on the results of decoding, RS 420 may process the data (step780). In one exemplary embodiment, RS 420 may process the data by, forexample, forwarding the frame to the next RS 420 in the transmissionpath. Alternatively, RS 420 may drop the frame. That is, RS 420 a mayforward data to nodes which are in the transmission path for RS 420 a,and drop data that is destined for nodes not in the transmission path ofRS 420. In this manner, BS 410 may send frame data to a destination SS430 by means of one or more RSs 420 using a tag-switched control data.

FIG. 8 a is an exemplary flow chart 800 a illustrating processing of anuplink communication received from RS 420 by BS 410. BS 410 may receivenotification of an upcoming data transmission (step 805). BS 410 mayidentify a transmission path for the data transmission (step 810), andmay allocate resources along the upstream transmission path (step 815).In addition, BS 410 may assign tag-switched control data transmissionparameters for SS 430 and RSs 420 along the transmission path (step820). BS 410 may transmit a control message (i.e., MAP message)containing the transmission parameters to SS 430 (step 825), and waitfor data from SS 430 (step 830).

FIG. 8 b is an exemplary flow chart 800 b illustrating processing of anuplink communication received by RS 420 from SS 430. RS 420 may receivea MAP message from BS 410 (step 850). RS 420 may identify the controldata (step 855), and wait for uplink data from SS 430 or a subordinateRS 420 (step 860). If the uplink data is from SS 430 (step 865, Yes), RS420 may transmit the data received from SS 430 to BS 410 using thetag-switched control data (step 870). If the data is not from SS 430(step 865, No), RS 420 may transfer the received data directly to BS 410(step 875).

FIG. 9 is a block diagram of an exemplary architecture 900 of RS 420,consistent with certain disclosed embodiments. Architecture 900 mayinclude a reception unit 910, a buffer unit 920, a transmission unit930, and a control unit 940. Reception unit 910 may be configured toreceive data from one or more BSs 410, SSs 430, and other RSs 420, andmay be configured to process the received data. Buffer unit 920 may beconfigured to buffer the data processed by reception unit 910. Forexample, buffer unit 920 may identify the data, modify the data, etc.Control unit 940 may be configured to determine if incoming dataincludes packet data or control data, i.e., MAP message. If the incomingdata is packet data, control unit 940 may be configured to perform oneor more processes including, for example, retransmission, fragmentation,packing, etc. If the incoming data is a MAP message, control unit 940may be configured to modify the control data. In addition, control unit940 may be configured to determine one or more parameters for receptionunit 910 and transmission unit 930. Transmission unit 930 may beconfigured to perform pre-processing on data sent from buffer unit 920based on one or more parameters determined by control unit 940.Transmission unit 930 may also be configured to transmit data to one ormore BSs 410, SSs 430, and other RSs 420.

FIG. 10 is a flow chart 1000 of exemplary processing by RS 420 usingarchitecture 900, consistent with certain disclosed embodiments. Datasent from one or more BSs 410, SSs 430, and other RSs 420 may bereceived by reception unit 910 of RS 420 (step 1005). Reception unit 910may perform processing on the received data (step 1010). Processing mayinclude, for example, decoding, demodulation, translating analog radiosignals to digital radio signals, etc.

Based on information provided by the reception unit 910, control unit940 may determine if the received data is a MAP message (step 1015). Ifthe received data is a MAP message (step 1015, Yes), control unit 940may identify one or more control data in the MAP, e.g., MAP IEs. Controlunit 940 may determine if the control data is intended for itself or ifthe control data is to be relayed to another RS 420 or on to BS 410(step 1025). If the control data is intended for the current RS 420,control unit 940 may configure reception unit 910 to receive thefollowing data burst in a defined time slot and sub-channel according tothe transmission parameters contained in the connection-switched controldata. If the control unit 940 determines that the control data is notintended for itself, control unit 940 may look up the tag information inRS tag table 450 to determine the next node in the transmission path. Inaddition, control unit 940 may determine one or more transmissionparameters, and forward the control data to transmission unit 930.Transmission unit 930 may perform pre-processing on the received controldata (step 1030), and transmit the data according to the transmissionparameters determined by control unit 940 (step 1035).

If the received data is not control data (step 1015, No), control unit940 may perform data processing (step 1020). For example, control unit940 of the receiving RS 420 may configure the transmission unit 930 toforward the burst to the next node without further processing. If thereceived data is packet data and intended for the receiving RS 420,control unit 940 may decode the control data embedded in the burstand/or configured during connection setup. Control unit 940 may alsoconfigure transmission unit 930 to transmit the relatedconnection-switched control data and packet data for one or more SSs 430within its coverage in the indicated time slot and sub-channel (step1025), and forward the data to transmission unit 930. Transmission unit930 may perform pre-processing on the received control data (step 1030),and transmit the data according to the transmission parametersdetermined by control unit 940 (step 1035).

FIG. 11 is a diagram illustrating an exemplary communication from BS 110in tag-switched network 400. As shown in FIG. 11, network 400 has beenexpanded to include RSs 420 d, 420 e, and 420 f, and SSs 430 s, 430 t,430 u, and 430 z. In one exemplary embodiment, BS 110 may store one ormore BS tag tables 440. The one or more BS tag tables 440 may includedata associated with one or more relay nodes, one or more transmissionpaths, and/or one or more transmission path identifiers. As shown inFIG. 11, BS tag table 440 may identify six transmission paths,transmission path 1 (i.e., the transmission path from BS 410 to RS 420a), transmission path 2 (i.e., the transmission path from BS 410 to RS420 b), transmission path 3 (i.e., the transmission path from BS 410 toRS 420 c), transmission path 4 (i.e., the transmission path from BS 410to RS 420 d), transmission path 5 (i.e., the transmission path from BS410 to RS 420 e), and transmission path 6 (i.e., the transmission pathfrom BS 410 to RS 4200.

In addition, BS tag table 440 may identify relationships between, one ormore transmission paths and one or more SSs 430. For example, BS tagtable 440 may identify SS 430 t (i.e., “t”) as communicating by means oftransmission path 1, SS 430 u (i.e., “u”) as communicating by means oftransmission path 2, SSs 430 w, 430 x and 430 y (i.e., “w,” “x,” and“v”) as communicating by means of transmission path 3, and SS 430 z(i.e., “z”) as communicating by means of transmission path 6. Inaddition, BS tag table 440 may indicate that SS 430 s is communicatingby means of BS 410. While BS tag table 440 shows no duplication oroverlap of service provided to SSs 430, it is possible that a single SS430 may receive service by means of more than one transmission path. Forexample, SS 430 y may receive service from RS 420 c and RS 420 f, thusSS 430 y may be associated with the transmission paths to RS 420 c andRS 420 f. As represented in FIG. 11, “y” would appear not only in thesame row as “3,” as shown in BS tag table 440, but also in the same rowas “6” (not shown).

In one exemplary embodiment, each RS 420 may store one or more RS tagtables 450. Because RS 420 a is the dominant RS 420 for RS 420 b, RS 420c, RS 420 e, and RS 420 f, and thus is in the transmission path to eachof those subordinate RSs 420, RS tag table 450 a may, for example,identify four transmission paths: transmission path 2 (i.e., thetransmission path to RS 420 b), transmission path 3 (i.e., thetransmission path to RS 420 c), transmission path 5 (i.e., thetransmission path to RS 420 e), and transmission path 6 (i.e., thetransmission path to RS 4200. In addition, RS tag table 450 a mayindicate that SS 430 t is serviced by RS 420 a. Because RS 420 b is thedominant RS 420 for RS 420 c and RS 420 f, and thus is in thetransmission path to each of it subordinate RSs 420, RS tag table 450 bmay identify two transmission paths: transmission path 3 (i.e., thetransmission path to RS 420 c) and transmission path 6 (i.e., thetransmission path to RS 420 f). In addition, RS tag table 450 b mayindicate that SS 430 u is serviced by RS 420 b. RS tag table 450 c of RS420 c may contain no transmission path information because RS 420 c hasno subordinate RSs 420. However, RS tag table 450 c may indicate that SS430 w, SS 430 x, and SS 430 y are serviced by RS 420 c. Similarly, RStag table 450 f of RS 420 f may contain no transmission path informationbecause RS 420 f has no subordinate RSs 420. However, RS tag table 450 fmay indicate that SS 430 z is serviced by RS 420 f. RS 420 d and RS 420e may have no RS tag tables 450 or may have no data in their RS tagtables 450 because RS 420 d and RS 420 e have no subordinate RSs 420 anddo not provide service to any SSs 430.

In the example of FIG. 11, BS 410 may receive data for SS 430 s, SS 430t, SS 430 u, SS 430 w, SS 430 x, SS 430 y, and SS 430 z. BS 410 mayaccess BS tag table 440 to determine transmission paths for each SS 430,and may generate a tag-switched MAP IF for each transmission path. Inaddition, BS 410 may generate a connection-switched control data foreach SS 430 receiving data. BS 410 may place the connection-switchedcontrol data in a data burst area, and may place the associatedtag-switched control data in frame MAP IE slots, the MAC header, orboth. For example, referring to a data frame 460 between BS 410 and RS420 a, BS 410 may send a frame containing four tag-switched controldata, each tag-switched control data associated with a data burst areaof the frame. That is, tag-switched control data 1 may correspond todata burst area t, tag-switched control data 2 may correspond to databurst area u, tag-switched control data 3 may correspond to data burstarea wxy, and tag-switched control data 6 may correspond to data burstarea z. Once BS 410 has completed processing the frame, BS 410 maytransmit the frame to the next node in the transmission path, i.e., RS420 a.

RS 420 a may receive data frame 460 and may process each tag-switchedcontrol data. In this example, data frame 460 may contain fourtag-switched control data. RS 420 a may determine that the tag containedin tag-switched control data 1 identifies RS 420 a, and RS 420 a maydecode the connection-switched control data in data burst area t. RS 420a may transmit the associated data, also contained in data burst area t,to SS 430 t according to the connection-switched control dataparameters.

RS 420 a may determine that tag-switched control data 2, 3, and 6 arenot intended for RS 420 a, and RS 420 a may access RS tag table 450 ausing the tags found in the tag-switched control data to determine thenext node in the transmission path for each one. In this example, RS 420a may determine that RS 420 b is the next node, and RS 420 a may forwardthe remaining frame data to RS 420 b as a data frame 470. If, however,RS 420 a determines that the next node is not in the transmission pathof RS 420 a, RS 420 a may drop the frame. For example, RS 420 a mayforward data to RS 420 b and RS 420 e, and drop data destined for RS 420d.

RS 420 b may receive data frame 470 and may process each tag-switchedcontrol data. In this example, data frame 470 may contain threetag-switched control data. RS 420 b may determine that the tag containedin tag-switched control data 2 identifies RS 420 b, and RS 420 b maydecode the connection-switched control data in corresponding data burstarea u. RS 420 b may transmit the associated data, also contained indata burst area u, to SS 430 u according to the connection-switchedcontrol data parameters.

RS 420 b may determine that frame control data 3 and 6 are not intendedfor RS 420 b, and RS 420 b may access RS tag table 450 b using the tagsfound in the tag-switched control data to determine the next node in thetransmission path. In this example, RS 420 b may determine that RS 420 cis the next node for the frame data corresponding to control data 3, andRS 420 f is the next node for the frame data corresponding to controldata 6. RS 420 b may forward the frame data corresponding to controldata 3 to RS 420 c as a data frame 480, and may forward the frame datacorresponding to control data 6 to RS 420 f as a data frame 490. If,however, RS 420 b determines that the next node is not in thetransmission path of RS 420 b, RS 420 b may drop the frame. For example,RS 420 b may forward data to RS 420 c and RS 420 f, and drop datadestined for RS 420 d and RS 420 e.

RS 420 c may receive data frame 480 and may process each tag-switchedcontrol data. In this example, data frame 480 may contain only onetag-switched control data. RS 420 c may determine that the tag containedin tag-switched control data 3 identifies RS 420 c, and RS 420 c maydecode the connection-switched control data in data burst area wxy. RS420 c may transmit the associated data, also contained in data burstarea wxy, to SS 430 w, SS 430 x, and SS 430 y according to theconnection-switched control data parameters for each SS 430.

Similarly, RS 420 f may receive data frame 490 and process eachtag-switched control data. In this example, data frame 490 may containonly one tag-switched control data. RS 420 f may determine that the tagcontained in the tag-switched control data 6 identifies RS 420 f, and RS420 f may decode the connection-switched control data in data burst areaz. RS 420 f may transmit the associated data, also contained in databurst area z, to SS 430 z according to the connection-switched controldata.

In this manner, network 400 may transmit and receive data using one ormore relay nodes by replacing one or more connection-switched controldata with one or more tag-switched control data.

Although the disclosed embodiments show a tag-switched network based onthe IEEE 802.16 family of standards, the disclosed embodiments may beimplemented within any network utilizing one or more network nodes,which may be configured to transmit or retransmit data to one or moreother network nodes. The disclosed embodiments may achieve improvedperformance. In particular, the disclosed embodiments may provide asimplified network node architecture, improve management of wirelesscommunication connections, increase the speed of packet switchprocessing, and improve resource utilization.

It will be apparent to those skilled in the art that variousmodifications and variations can be made in the system and method fortag-switched wireless transmission. It is intended that the standard andexamples be considered as exemplary only, with a true scope of thedisclosed embodiments being indicated by the following claims and theirequivalents.

What is claimed is:
 1. A method for performing data processing in anintermediary node in a wireless communication network, comprising:receiving, by a reception unit, transmission data, wherein thetransmission data includes at least one first control data and at leastone second control data, wherein each of the at least one first controldata includes a connection identifier and each of the at least onesecond control data includes a transmission path identifier, wherein thetransmission path identifier is a destination node identifier, thetransmission path identifier includes information identifying at leastone destination node, and the transmission path identifier does notinclude information identifying the intermediary node; processing, bythe reception unit, the transmission data; buffering, by a buffer unitin communication with the reception unit, the processed data; receiving,by a transmission unit in communication with the buffer unit, thebuffered data from the buffer unit; performing pre-transmissionprocessing on the buffered data; and configuring, by a control unit incommunication with the reception unit, the buffer unit, and thetransmission unit, one or more reception parameters associated with thereception unit.
 2. The method as in claim 1, further including:configuring, by the control unit, one or more transmission parametersassociated with the transmission unit.
 3. The method as in claim 2,further including: processing, by the transmission unit, the buffereddata received from the buffer unit based on the one or more transmissionparameters configured by the control unit.
 4. The method as in claim 1,further including: determining, by the control unit, if the transmissiondata includes control data.
 5. The method as in claim 4, wherein if itis determined that the transmission data includes control data,identifying each of the at least one second control data.
 6. The methodas in claim 1, further including: determining if the transmission datais intended for the destination node based on the transmission pathidentifier.
 7. The method as in claim 1, wherein the first control datais a first MAP Information Element (IE) and the second control data is asecond MAP IE.
 8. The method as in claim 1, wherein the wirelesscommunication network further includes at least one control node.
 9. Themethod as in claim 8, wherein the at least one control node is a basestation.
 10. The method as in claim 8, wherein the at least one controlnode is a relay station.
 11. The method as in claim 1, wherein thedestination node identifier identifies at least one destination node.12. An intermediary node for performing data processing in a wirelesscommunication network, comprising: a reception unit operable to receiveand process transmission data, wherein the transmission data includes atleast one first control data and at least one second control data,wherein each of the at least one first control data includes aconnection identifier and each of the at least one second control dataincludes a transmission path identifier, wherein the transmission pathidentifier is a destination node identifier, the transmission pathidentifier includes information identifying at least one destinationnode, and the transmission path identifier does not include informationidentifying the intermediary node; a buffer unit in communication withthe reception unit and configured to buffer the processed data; atransmission unit in communication with the buffer unit and configuredto receive the buffered data from the buffer unit; and a control unit incommunication with the reception unit, the buffer unit, and thetransmission unit, and operable to configure one or more receptionparameters associated with the reception unit.
 13. The intermediary nodeas in claim 12, wherein the control unit is further in communicationwith the transmission unit and operable to configure one or moretransmission parameters associated with the transmission unit.
 14. Theintermediary node as in claim 13, wherein the transmission unit isfurther configured to: process the buffered data received from thebuffer unit based on the one or more transmission parameters configuredby the control unit.
 15. The intermediary node as in claim 12, whereinthe control unit is configured to determine if the transmission dataincludes control data.
 16. The intermediary node as in claim 12, whereinwhen the control unit determines that the transmission data includescontrol data, the control unit is further configured to identify the atleast one second control data.
 17. The intermediary node as in claim 12,wherein the control unit is further configured to: determine if thetransmission data is intended for the destination node based on thetransmission path identifier.
 18. The intermediary node as in claim 12,wherein the first control data is a first MAP Information Element (IE)and the second control data is a second MAP IE.
 19. The intermediarynode as in claim 12, wherein the wireless communication network furtherincludes at least one control node.
 20. The intermediary node as inclaim 19, wherein the at least one control node is a base station. 21.The intermediary node as in claim 19, wherein the at least one controlnode is a relay station.
 22. The intermediary node as in claim 12,wherein the destination node identifier identifies at least onedestination node.